Dispersed storage write process

ABSTRACT

A dispersed storage (DS) method begins by issuing a plurality of write commands to a plurality of DS storage units. The method continues by receiving a write acknowledgement from one of the plurality of DS storage units to produce a received write acknowledgement. The method continues by issuing a plurality of commit commands to the plurality of DS storage units when a write threshold number of the received write acknowledgements have been received. The method continues by receiving a commit acknowledgement from a DS storage unit of the plurality of DS storage units to produce a received commit acknowledgement. The method continues by issuing a plurality of finalize commands to the plurality of DS storage units when a write threshold number of the received commit acknowledgements have been received.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/230,038, entitled “DISPERSED STORAGE NETWORK VERSION SYNCHRONIZATION,” filed Jul. 30, 2009, pending, which is hereby incorporated herein by reference in its entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

NOT APPLICABLE

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

NOT APPLICABLE

BACKGROUND OF THE INVENTION

1. Technical Field of the Invention

This invention relates generally to computing systems and more particularly to data storage solutions within such computing systems.

2. Description of Related Art

Computers are known to communicate, process, and store data. Such computers range from wireless smart phones to data centers that support millions of web searches, stock trades, or on-line purchases every day. In general, a computing system generates data and/or manipulates data from one form into another. For instance, an image sensor of the computing system generates raw picture data and, using an image compression program (e.g., JPEG, MPEG, etc.), the computing system manipulates the raw picture data into a standardized compressed image.

With continued advances in processing speed and communication speed, computers are capable of processing real time multimedia data for applications ranging from simple voice communications to streaming high definition video. As such, general-purpose information appliances are replacing purpose-built communications devices (e.g., a telephone). For example, smart phones can support telephony communications but they are also capable of text messaging and accessing the internet to perform functions including email, web browsing, remote applications access, and media communications (e.g., telephony voice, image transfer, music files, video files, real time video streaming, etc.).

Each type of computer is constructed and operates in accordance with one or more communication, processing, and storage standards. As a result of standardization and with advances in technology, more and more information content is being converted into digital formats. For example, more digital cameras are now being sold than film cameras, thus producing more digital pictures. As another example, web-based programming is becoming an alternative to over the air television broadcasts and/or cable broadcasts. As further examples, papers, books, video entertainment, home video, etc. are now being stored digitally, which increases the demand on the storage function of computers.

A typical computer storage system includes one or more memory devices aligned with the needs of the various operational aspects of the computer's processing and communication functions. Generally, the immediacy of access dictates what type of memory device is used. For example, random access memory (RAM) memory can be accessed in any random order with a constant response time, thus it is typically used for cache memory and main memory. By contrast, memory device technologies that require physical movement such as magnetic disks, tapes, and optical discs, have a variable response time as the physical movement can take longer than the data transfer, thus they are typically used for secondary memory (e.g., hard drive, backup memory, etc.).

A computer's storage system will be compliant with one or more computer storage standards that include, but are not limited to, network file system (NFS), flash file system (FFS), disk file system (DFS), small computer system interface (SCSI), internet small computer system interface (iSCSI), file transfer protocol (FTP), and web-based distributed authoring and versioning (WebDAV). These standards specify the data storage format (e.g., files, data objects, data blocks, directories, etc.) and interfacing between the computer's processing function and its storage system, which is a primary function of the computer's memory controller.

Despite the standardization of the computer and its storage system, memory devices fail; especially commercial grade memory devices that utilize technologies incorporating physical movement (e.g., a disc drive). For example, it is fairly common for a disc drive to routinely suffer from bit level corruption and to completely fail after three years of use. One solution is to a higher-grade disc drive, which adds significant cost to a computer.

Another solution is to utilize multiple levels of redundant disc drives to replicate the data into two or more copies. One such redundant drive approach is called redundant array of independent discs (RAID). In a RAID device, a RAID controller adds parity data to the original data before storing it across the array. The parity data is calculated from the original data such that the failure of a disc will not result in the loss of the original data. For example, RAID 5 uses three discs to protect data from the failure of a single disc. The parity data, and associated redundancy overhead data, reduces the storage capacity of three independent discs by one third (e.g., n−1=capacity). RAID 6 can recover from a loss of two discs and requires a minimum of four discs with a storage capacity of n−2.

While RAID addresses the memory device failure issue, it is not without its own failures issues that affect its effectiveness, efficiency and security. For instance, as more discs are added to the array, the probability of a disc failure increases, which increases the demand for maintenance. For example, when a disc fails, it needs to be manually replaced before another disc fails and the data stored in the RAID device is lost. To reduce the risk of data loss, data on a RAID device is typically copied on to one or more other RAID devices. While this addresses the loss of data issue, it raises a security issue since multiple copies of data are available, which increases the chances of unauthorized access. Further, as the amount of data being stored grows, the overhead of RAID devices becomes a non-trivial efficiency issue.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a computing system in accordance with the invention;

FIG. 2 is a schematic block diagram of an embodiment of a computing core in accordance with the invention;

FIG. 3 is a schematic block diagram of an embodiment of a dispersed storage processing module in accordance with the invention;

FIG. 4 is a schematic block diagram of an embodiment of a grid module in accordance with the invention;

FIG. 5 is a schematic block diagram of an embodiment of a computing core in accordance with the invention;

FIG. 6 is a state diagram of an example embodiment of a dispersed storage system in accordance with the invention;

FIG. 7 is a schematic block diagram of an embodiment of a dispersed storage system in accordance with the invention;

FIG. 8 is a schematic block diagram of another embodiment of a dispersed storage system in accordance with the invention;

FIG. 9 is a schematic block diagram of another embodiment of a dispersed storage system in accordance with the invention;

FIG. 10 is a schematic block diagram of another embodiment of a dispersed storage system in accordance with the invention; and

FIG. 11 is a schematic block diagram of another embodiment of a dispersed storage system in accordance with the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of a computing system 10 that includes one or more of a first type of user devices 12, one or more of a second type of user devices 14, at least one distributed storage (DS) processing unit 16, at least one DS managing unit 18, at least one storage integrity processing unit 20, and a distributed storage network (DSN) memory 22 coupled via a network 24. The network 24 may include one or more wireless and/or wire lined communication systems; one or more private intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

The DSN memory 22 includes a plurality of distributed storage (DS) units 36 for storing data of the system. Each of the DS units 36 includes a processing module and memory and may be located at a geographically different site than the other DS units (e.g., one in Chicago, one in Milwaukee, etc.). The processing module may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that when the processing module implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element stores, and the processing module executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 1-11.

Each of the user devices 12-14, the DS processing unit 16, the DS managing unit 18, and the storage integrity processing unit 20 may be a portable computing device (e.g., a social networking device, a gaming device, a cell phone, a smart phone, a personal digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a video game controller, and/or any other portable device that includes a computing core) and/or a fixed computing device (e.g., a personal computer, a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment). Such a portable or fixed computing device includes a computing core 26 and one or more interfaces 30, 32, and/or 33. An embodiment of the computing core 26 will be described with reference to FIG. 2.

With respect to the interfaces, each of the interfaces 30, 32, and 33 includes software and/or hardware to support one or more communication links via the network 24 and/or directly. For example, interfaces 30 support a communication link (wired, wireless, direct, via a LAN, via the network 24, etc.) between the first type of user device 14 and the DS processing unit 16. As another example, DSN interface 32 supports a plurality of communication links via the network 24 between the DSN memory 22 and the DS processing unit 16, the first type of user device 12, and/or the storage integrity processing unit 20. As yet another example, interface 33 supports a communication link between the DS managing unit 18 and any one of the other devices and/or units 12, 14, 16, 20, and/or 22 via the network 24.

In general and with respect to data storage, the system 10 supports three primary functions: distributed network data storage management, distributed data storage and retrieval, and data storage integrity verification. In accordance with these three primary functions, data can be distributedly stored in a plurality of physically different locations and subsequently retrieved in a reliable and secure manner regardless of failures of individual storage devices, failures of network equipment, the duration of storage, the amount of data being stored, attempts at hacking the data, etc.

The DS managing unit 18 performs distributed network data storage management functions, which include establishing distributed data storage parameters, performing network operations, performing network administration, and/or performing network maintenance. The DS managing unit 18 establishes the distributed data storage parameters (e.g., allocation of virtual DSN memory space, distributed storage parameters, security parameters, billing information, user profile information, etc.) for one or more of the user devices 12-14 (e.g., established for individual devices, established for a user group of devices, established for public access by the user devices, etc.). For example, the DS managing unit 18 coordinates the creation of a vault (e.g., a virtual memory block) within the DSN memory 22 for a user device (for a group of devices, or for public access). The DS managing unit 18 also determines the distributed data storage parameters for the vault. In particular, the DS managing unit 18 determines a number of slices (e.g., the number that a data segment of a data file and/or data block is partitioned into for distributed storage) and a read threshold value (e.g., the minimum number of slices required to reconstruct the data segment).

As another example, the DS managing module 18 creates and stores, locally or within the DSN memory 22, user profile information. The user profile information includes one or more of authentication information, permissions, and/or the security parameters. The security parameters may include one or more of encryption/decryption scheme, one or more encryption keys, key generation scheme, and data encoding/decoding scheme.

As yet another example, the DS managing unit 18 creates billing information for a particular user, user group, vault access, public vault access, etc. For instance, the DS managing unit 18 tracks the number of times user accesses a private vault and/or public vaults, which can be used to generate a per-access bill. In another instance, the DS managing unit 18 tracks the amount of data stored and/or retrieved by a user device and/or a user group, which can be used to generate a per-data-amount bill.

The DS managing unit 18 also performs network operations, network administration, and/or network maintenance. As at least part of performing the network operations and/or administration, the DS managing unit 18 monitors performance of the devices and/or units of the system 10 for potential failures, determines the devices and/or unit's activation status, determines the devices' and/or units' loading, and any other system level operation that affects the performance level of the system 10. For example, the DS managing unit 18 receives and aggregates network management alarms, alerts, errors, status information, performance information, and messages from the devices 12-14 and/or the units 16, 20, 22. For example, the DS managing unit 18 receives a simple network management protocol (SNMP) message regarding the status of the DS processing unit 16.

The DS managing unit 18 performs the network maintenance by identifying equipment within the system 10 that needs replacing, upgrading, repairing, and/or expanding. For example, the DS managing unit 18 determines that the DSN memory 22 needs more DS units 36 or that one or more of the DS units 36 needs updating.

The second primary function (i.e., distributed data storage and retrieval) begins and ends with a user device 12-14. For instance, if a second type of user device 14 has a data file 38 and/or data block 40 to store in the DSN memory 22, it send the data file 38 and/or data block 40 to the DS processing unit 16 via its interface 30. As will be described in greater detail with reference to FIG. 2, the interface 30 functions to mimic a conventional operating system (OS) file system interface (e.g., network file system (NFS), flash file system (FFS), disk file system (DFS), file transfer protocol (FTP), web-based distributed authoring and versioning (WebDAV), etc.) and/or a block memory interface (e.g., small computer system interface (SCSI), internet small computer system interface (iSCSI), etc.). In addition, the interface 30 may attach a user identification code (ID) to the data file 38 and/or data block 40.

The DS processing unit 16 receives the data file 38 and/or data block 40 via its interface 30 and performs a distributed storage (DS) process 34 thereon (e.g., an error coding dispersal storage function). The DS processing 34 begins by partitioning the data file 38 and/or data block 40 into one or more data segments, which is represented as Y data segments. For example, the DS processing 34 may partition the data file 38 and/or data block 40 into a fixed byte size segment (e.g., 2¹ to 2^(n) bytes, where n=>2) or a variable byte size (e.g., change byte size from segment to segment, or from groups of segments to groups of segments, etc.).

For each of the Y data segments, the DS processing 34 error encodes (e.g., forward error correction (FEC), information dispersal algorithm, or error correction coding) and slices (or slices then error encodes) the data segment into a plurality of error coded (EC) data slices 42-48, which is represented as X slices per data segment. The number of slices (X) per segment, which corresponds to a number of pillars n, is set in accordance with the distributed data storage parameters and the error coding scheme. For example, if a Reed-Solomon (or other FEC scheme) is used in an n/k system, then a data segment is divided into n slices, where k number of slices is needed to reconstruct the original data (i.e., k is the threshold). As a few specific examples, the n/k factor may be 5/3; 6/4; 8/6; 8/5; 16/10.

For each slice 42-48, the DS processing unit 16 creates a unique slice name and appends it to the corresponding slice 42-48. The slice name includes universal DSN memory addressing routing information (e.g., virtual memory addresses in the DSN memory 22) and user-specific information (e.g., user ID, file name, data block identifier, etc.).

The DS processing unit 16 transmits the plurality of EC slices 42-48 to a plurality of DS units 36 of the DSN memory 22 via the DSN interface 32 and the network 24. The DSN interface 32 formats each of the slices for transmission via the network 24. For example, the DSN interface 32 may utilize an internet protocol (e.g., TCP/IP, etc.) to packetize the slices 42-48 for transmission via the network 24.

The number of DS units 36 receiving the slices 42-48 is dependent on the distributed data storage parameters established by the DS managing unit 18. For example, the DS managing unit 18 may indicate that each slice is to be stored in a different DS unit 36. As another example, the DS managing unit 18 may indicate that like slice numbers of different data segments are to be stored in the same DS unit 36. For example, the first slice of each of the data segments is to be stored in a first DS unit 36, the second slice of each of the data segments is to be stored in a second DS unit 36, etc. In this manner, the data is encoded and distributedly stored at physically diverse locations to improved data storage integrity and security. Further examples of encoding the data segments will be provided with reference to one or more of FIGS. 2-11.

Each DS unit 36 that receives a slice 42-48 for storage translates the virtual DSN memory address of the slice into a local physical address for storage. Accordingly, each DS unit 36 maintains a virtual to physical memory mapping to assist in the storage and retrieval of data.

The first type of user device 12 performs a similar function to store data in the DSN memory 22 with the exception that it includes the DS processing. As such, the device 12 encodes and slices the data file and/or data block it has to store. The device then transmits the slices 35 to the DSN memory via its DSN interface 32 and the network 24.

For a second type of user device 14 to retrieve a data file or data block from memory, it issues a read command via its interface 30 to the DS processing unit 16. The DS processing unit 16 performs the DS processing 34 to identify the DS units 36 storing the slices of the data file and/or data block based on the read command. The DS processing unit 16 may also communicate with the DS managing unit 18 to verify that the user device 14 is authorized to access the requested data.

Assuming that the user device is authorized to access the requested data, the DS processing unit 16 issues slice read commands to at least a threshold number of the DS units 36 storing the requested data (e.g., to at least 10 DS units for a 16/10 error coding scheme). Each of the DS units 36 receiving the slice read command, verifies the command, accesses its virtual to physical memory mapping, retrieves the requested slice, or slices, and transmits it to the DS processing unit 16.

Once the DS processing unit 16 has received a read threshold number of slices for a data segment, it performs an error decoding function and de-slicing to reconstruct the data segment. When Y number of data segments has been reconstructed, the DS processing unit 16 provides the data file 38 and/or data block 40 to the user device 14. Note that the first type of user device 12 performs a similar process to retrieve a data file and/or data block.

The storage integrity processing unit 20 performs the third primary function of data storage integrity verification. In general, the storage integrity processing unit 20 periodically retrieves slices 45, and/or slice names, of a data file or data block of a user device to verify that one or more slices have not been corrupted or lost (e.g., the DS unit failed). The retrieval process mimics the read process previously described.

If the storage integrity processing unit 20 determines that one or more slices is corrupted or lost, it rebuilds the corrupted or lost slice(s) in accordance with the error coding scheme. The storage integrity processing unit 20 stores the rebuild slice, or slices, in the appropriate DS unit(s) 36 in a manner that mimics the write process previously described.

FIG. 2 is a schematic block diagram of an embodiment of a computing core 26 that includes a processing module 50, a memory controller 52, main memory 54, a video graphics processing unit 55, an input/output (IO) controller 56, a peripheral component interconnect (PCI) interface 58, at least one IO device interface module 62, a read only memory (ROM) basic input output system (BIOS) 64, and one or more memory interface modules. The memory interface module(s) includes one or more of a universal serial bus (USB) interface module 66, a host bus adapter (HBA) interface module 68, a network interface module 70, a flash interface module 72, a hard drive interface module 74, and a DSN interface module 76. Note the DSN interface module 76 and/or the network interface module 70 may function as the interface 30 of the user device 14 of FIG. 1. Further note that the IO device interface module 62 and/or the memory interface modules may be collectively or individually referred to as IO ports.

The processing module 50 may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module 50 may have an associated memory and/or memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of the processing module 50. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module 50 includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that when the processing module 50 implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element stores, and the processing module 50 executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in FIGS. 1-11.

FIG. 3 is a schematic block diagram of an embodiment of a dispersed storage (DS) processing module 34 of user device 12 and/or of the DS processing unit 16. The DS processing module 34 includes a gateway module 78, an access module 80, a grid module 82, and a storage module 84. The DS processing module 34 may also include an interface 30 and the DSnet interface 32 or the interfaces 68 and/or 70 may be part of user 12 or of the DS processing unit 14. The DS processing module 34 may further include a bypass/feedback path between the storage module 84 to the gateway module 78. Note that the modules 78-84 of the DS processing module 34 may be in a single unit or distributed across multiple units.

In an example of storing data, the gateway module 78 receives an incoming data object that includes a user ID field 86, an object name field 88, and the data field 40 and may also receive corresponding information that includes a process identifier (e.g., an internal process/application ID), metadata, a file system directory, a block number, a transaction message, a user device identity (ID), a data object identifier, a source name, and/or user information. The gateway module 78 authenticates the user associated with the data object by verifying the user ID 86 with the managing unit 18 and/or another authenticating unit.

When the user is authenticated, the gateway module 78 obtains user information from the management unit 18, the user device, and/or the other authenticating unit. The user information includes a vault identifier, operational parameters, and user attributes (e.g., user data, billing information, etc.). A vault identifier identifies a vault, which is a virtual memory space that maps to a set of DS storage units 36. For example, vault 1 (i.e., user 1's DSN memory space) includes eight DS storage units (X=8 wide) and vault 2 (i.e., user 2's DSN memory space) includes sixteen DS storage units (X=16 wide). The operational parameters may include an error coding algorithm, the width n (number of pillars X or slices per segment for this vault), a read threshold T, a write threshold, an encryption algorithm, a slicing parameter, a compression algorithm, an integrity check method, caching settings, parallelism settings, and/or other parameters that may be used to access the DSN memory layer.

The gateway module 78 uses the user information to assign a source name 35 to the data. For instance, the gateway module 60 determines the source name 35 of the data object 40 based on the vault identifier and the data object. For example, the source name may contain a file identifier (ID), a vault generation number, a reserved field, and a vault identifier (ID). As another example, the gateway module 78 may generate the file ID based on a hash function of the data object 40. Note that the gateway module 78 may also perform message conversion, protocol conversion, electrical conversion, optical conversion, access control, user identification, user information retrieval, traffic monitoring, statistics generation, configuration, management, and/or source name determination.

The access module 80 receives the data object 40 and creates a series of data segments 1 through Y 90-92 in accordance with a data storage protocol (e.g., file storage system, a block storage system, and/or an aggregated block storage system). The number of segments Y may be chosen or randomly assigned based on a selected segment size and the size of the data object. For example, if the number of segments is chosen to be a fixed number, then the size of the segments varies as a function of the size of the data object. For instance, if the data object is an image file of 4,194,304 eight bit bytes (e.g., 33,554,432 bits) and the number of segments Y=131,072, then each segment is 256 bits or 32 bytes. As another example, if segment sized is fixed, then the number of segments Y varies based on the size of data object. For instance, if the data object is an image file of 4,194,304 bytes and the fixed size of each segment is 4,096 bytes, the then number of segments Y=1,024. Note that each segment is associated with the same source name.

The grid module 82 receives the data segments and may manipulate (e.g., compression, encryption, cyclic redundancy check (CRC), etc.) each of the data segments before performing an error coding function of the error coding dispersal storage function to produce a pre-manipulated data segment. After manipulating a data segment, if applicable, the grid module 82 error encodes (e.g., Reed-Solomon, Convolution encoding, Trellis encoding, etc.) the data segment or manipulated data segment into X error coded data slices 42-44.

The value X, or the number of pillars (e.g., X=16), is chosen as a parameter of the error coding dispersal storage function. Other parameters of the error coding dispersal function include a read threshold T, a write threshold W, etc. The read threshold (e.g., T=10, when X=16) corresponds to the minimum number of error-free error coded data slices required to reconstruct the data segment. In other words, the DS processing module 34 can compensate for X−T (e.g., 16−10=6) missing error coded data slices per data segment. The write threshold W corresponds to a minimum number of DS storage units that acknowledge proper storage of their respective data slices before the DS processing module indicates proper storage of the encoded data segment. Note that the write threshold is greater than or equal to the read threshold for a given number of pillars (X).

For each data slice of a data segment, the grid module 82 generates a unique slice name 37 and attaches it thereto. The slice name 37 includes a universal routing information field and a vault specific field and may be 48 bytes (e.g., 24 bytes for each of the universal routing information field and the vault specific field). As illustrated, the universal routing information field includes a slice index, a vault ID, a vault generation, and a reserved field. The slice index is based on the pillar number and the vault ID and, as such, is unique for each pillar (e.g., slices of the same pillar for the same vault for any segment will share the same slice index). The vault specific field includes a data name, which includes a file ID and a segment number (e.g., a sequential numbering of data segments 1-Y of a simple data object or a data block number).

Prior to outputting the error coded data slices of a data segment, the grid module may perform post-slice manipulation on the slices. If enabled, the manipulation includes slice level compression, encryption, CRC, addressing, tagging, and/or other manipulation to improve the effectiveness of the computing system.

When the error coded data slices of a data segment are ready to be outputted, the grid module 82 determines which of the DS storage units 36 will store the EC data slices based on a dispersed storage memory mapping associated with the user's vault and/or DS storage unit 36 attributes. The DS storage unit attributes may include availability, self-selection, performance history, link speed, link latency, ownership, available DSN memory, domain, cost, a prioritization scheme, a centralized selection message from another source, a lookup table, data ownership, and/or any other factor to optimize the operation of the computing system. Note that the number of DS storage units 36 is equal to or greater than the number of pillars (e.g., X) so that no more than one error coded data slice of the same data segment is stored on the same DS storage unit 36. Further note that EC data slices of the same pillar number but of different segments (e.g., EC data slice 1 of data segment 1 and EC data slice 1 of data segment 2) may be stored on the same or different DS storage units 36.

The storage module 84 performs an integrity check on the outbound encoded data slices and, when successful, identifies a plurality of DS storage units based on information provided by the grid module. The storage module then outputs the encoded data slices 1 through X of each segment 1 through Y to the DS storage units. Each of the DS storage units 36 stores its EC data slice(s) and maintains a local virtual DSN address to physical location table to convert the virtual DSN address of the EC data slice(s) into physical storage addresses.

In an example of a read operation, the user device 12 and/or 14 sends a read request to the DS processing unit 14, which authenticates the request. When the request is authentic, the DS processing unit 14 sends a read message to each of the DS storage units 36 storing slices of the data object being read. The slices are received via the DSnet interface 32 and processed by the storage module 84, which performs a parity check and provides the slices to the grid module 82 when the parity check was successful. The grid module 82 decodes the slices in accordance with the error coding dispersal storage function to reconstruct the data segment. The access module 80 reconstructs the data object from the data segments and the gateway module 78 formats the data object for transmission to the user device.

FIG. 4 is a schematic block diagram of an embodiment of a grid module 82 that includes a control unit 73, a pre-slice manipulator 75, an encoder 77, a slicer 79, a post-slice manipulator 81, a pre-slice de-manipulator 83, a decoder 85, a de-slicer 87, and/or a post-slice de-manipulator 89. Note that the control unit 73 may be partially or completely external to the grid module 82. For example, the control unit 73 may be part of the computing core at a remote location, part of a user device, part of the DS managing unit 18, or distributed amongst one or more DS storage units.

In an example of write operation, the pre-slice manipulator 75 receives a data segment 90-92 and a write instruction from an authorized user device. The pre-slice manipulator 75 determines if pre-manipulation of the data segment 90-92 is required and, if so, what type. The pre-slice manipulator 75 may make the determination independently or based on instructions from the control unit 73, where the determination is based on a computing system-wide predetermination, a table lookup, vault parameters associated with the user identification, the type of data, security requirements, available DSN memory, performance requirements, and/or other metadata.

Once a positive determination is made, the pre-slice manipulator 75 manipulates the data segment 90-92 in accordance with the type of manipulation. For example, the type of manipulation may be compression (e.g., Lempel-Ziv-Welch, Huffman, Golomb, fractal, wavelet, etc.), signatures (e.g., Digital Signature Algorithm (DSA), Elliptic Curve DSA, Secure Hash Algorithm, etc.), watermarking, tagging, encryption (e.g., Data Encryption Standard, Advanced Encryption Standard, etc.), adding metadata (e.g., time/date stamping, user information, file type, etc.), cyclic redundancy check (e.g., CRC32), and/or other data manipulations to produce the pre-manipulated data segment.

The encoder 77 encodes the pre-manipulated data segment 92 using a forward error correction (FEC) encoder (and/or other type of erasure coding and/or error coding) to produce an encoded data segment 94. The encoder 77 determines which forward error correction algorithm to use based on a predetermination associated with the user's vault, a time based algorithm, user direction, DS managing unit direction, control unit direction, as a function of the data type, as a function of the data segment 92 metadata, and/or any other factor to determine algorithm type. The forward error correction algorithm may be Golay, Multidimensional parity, Reed-Solomon, Hamming, Bose Ray Chauduri Hocquenghem (BCH), Cauchy-Reed-Solomon, or any other FEC encoder. Note that the encoder 77 may use a different encoding algorithm for each data segment 92, the same encoding algorithm for the data segments 92 of a data object, or a combination thereof.

The encoded data segment 94 is of greater size than the data segment 92 by the overhead rate of the encoding algorithm by a factor of X/T, where X is the width or number of slices, and T is the read threshold. In this regard, the corresponding decoding process can accommodate at most X−T missing EC data slices and still recreate the data segment 92. For example, if X=16 and T=10, then the data segment 92 will be recoverable as long as 10 or more EC data slices per segment are not corrupted.

The slicer 79 transforms the encoded data segment 94 into EC data slices in accordance with the slicing parameter from the vault for this user and/or data segment 92. For example, if the slicing parameter is X=16, then the slicer slices each encoded data segment 94 into 16 encoded slices.

The post-slice manipulator 81 performs, if enabled, post-manipulation on the encoded slices to produce the EC data slices. If enabled, the post-slice manipulator 81 determines the type of post-manipulation, which may be based on a computing system-wide predetermination, parameters in the vault for this user, a table lookup, the user identification, the type of data, security requirements, available DSN memory, performance requirements, control unit directed, and/or other metadata. Note that the type of post-slice manipulation may include slice level compression, signatures, encryption, CRC, addressing, watermarking, tagging, adding metadata, and/or other manipulation to improve the effectiveness of the computing system.

In an example of a read operation, the post-slice de-manipulator 89 receives at least a read threshold number of EC data slices and performs the inverse function of the post-slice manipulator 81 to produce a plurality of encoded slices. The de-slicer 87 de-slices the encoded slices to produce an encoded data segment 94. The decoder 85 performs the inverse function of the encoder 77 to recapture the data segment 90-92. The pre-slice de-manipulator 83 performs the inverse function of the pre-slice manipulator 75 to recapture the data segment.

FIG. 5 is a diagram of an example of slicing an encoded data segment 94 by the slicer 79. In this example, the encoded data segment includes thirty-two bits, but may include more or less bits. The slicer 79 disperses the bits of the encoded data segment 94 across the EC data slices in a pattern as shown. As such, each EC data slice does not include consecutive bits of the data segment 94 reducing the impact of consecutive bit failures on data recovery. For example, if EC data slice 2 (which includes bits 1, 5, 9, 13, 17, 25, and 29) is unavailable (e.g., lost, inaccessible, or corrupted), the data segment can be reconstructed from the other EC data slices (e.g., 1, 3 and 4 for a read threshold of 3 and a width of 4).

FIG. 6 is a state diagram of an example embodiment of a dispersed storage system implementing a write function. The diagram includes three states: a current version visible state 106, a dispersing new version state 108, and a new version visible, waiting to finalize state 110. The text between the states, which is in the form of “input”/“action”, indicates transitions between the states.

A write function begins in the current version visible state 106 (i.e., the data object is visible (e.g., accessible) in the DS storage units). The write function changes to the dispersing new version state 108 when the input of “new version to write” is received. For example, the DS processing module may receive a write command from a user device to store data. In this state 108, the DS processing module generates a plurality of error encoded data slices of the data, determines which DS storage units will store the data, and sends each of the DS storage units a write command.

While in the dispersing new version state 108, the DS processing module initializes a timeout period and waits to receive acknowledgements from the DS storage units. For example, when a DS storage unit receives its write command, the DS storage unit saves the EC data slice of the new version and send the write acknowledgement back to the DS processing module. As the DS processing module receives write acknowledgements, it determines whether it has received a write threshold number of acknowledgements (e.g., a number that exceeds the reconstruction threshold but less than the width or pillar number) prior to expiration of the timeout period. If not, the processing module issues a rollback commands to the DS storage units and the write function state reverts back to the current version visible state 106. Note that prior to issuing the rollback commands, the DS processing module may resend one or more of the plurality of write commands to the DS storage units.

If the number of received write acknowledgement equals or exceeds the write threshold (e.g., write acks≧write threshold), the DS processing module issues a plurality of commit commands to the DS storage units and the write function state changes to the new version visible & waiting to finalize state 110. The storage module may start a second timeout window. The DS storage unit may make the new version visible (e.g., it can be retrieved via the DSN as can the old version) 110 and the DS storage unit may send a commit acknowledgement to the storage module.

In this state 110, the DS processing module initializes another timeout period and waits to receive commit acknowledgements from the DS storage units. If the timeout period expires prior to receiving a write threshold number of commit acknowledgements, the DS processing module issues a plurality of undo commands to the DS storage units and the write function state reverts to the current version visible state 106. In response to receiving its undo command, a DS storage unit deletes the new version of the data (i.e., its EC data slice or slices).

If the DS processing module receives at least a write threshold number of commit acknowledgements, the DS processing module issues a plurality of finalize commands to the DS storage units and the write function state changes to the current version visible state 106. In this state, however, the data stored is now representative of the new data and not the old data.

FIGS. 7-11 are schematic block diagrams of an embodiment of a dispersed storage system that includes a storage module (i.e., the DS processing module) and a plurality of DS storage units 1-6. In an example, the DS storage units 1-6 form six pillars of a dispersed storage network (DSN) that has a pillar width of six, a write threshold of five, and a read or reconstruction threshold of four. The storage module may be part of one or more of the DS processing unit, the user device, the storage integrity processing unit, the DS managing unit, and/or the DS storage unit. The DS storage unit may be part of one or more of the user devices, a server, the DS processing unit, the DS managing unit, the storage integrity processing unit, and/or any device capable of storing information.

In the example of FIG. 7, the storage module sends write commands and new versions of data (e.g., EC data slices of a data segment) substantially in parallel (in time) to the DS storage units 1-6 and starts a timeout window. DS storage units 1-4 and 6 receive the new version of the data within the write command and store it. Even though DS units 1-4 and 6 receive and store the new version of the data, they maintain the old version of the data and their respective pointers point to the old version of data. In this regard, the new version of data is not visible and the old version of data is visible.

In this example, DS storage unit 5 does not receive the write command due to an error (e.g., a storage module error, a network communication error, a maintenance operation, a DS storage unit processing error, a DS storage unit storage error and/or any other error that affects receiving the write command). As such, DS storage unit 5 is not aware of the new version of data, but still stores the old version of the data in a visible manner (i.e., its pointer is pointing to old data).

In the example of FIG. 8, DS storage units 1-4 and 6 send respective write acknowledgements to the storage module indicating that they have received the write command and have stored the new version of data in an invisible manner (i.e., pointer points to the old version of data making it accessible). In addition to sending the acknowledgement, each DS storage unit starts a commit timeout period (e.g., a few millisecond to 10s of seconds). If a commit command (which is discussed with reference to FIG. 9) is not received prior to the expiration of the commit timeout period, the DS storage unit deletes the new version of data.

As the storage module receives the write command acknowledgements, it determines whether it has received a write threshold number of acknowledgements within the timeout period. For this example, the write threshold is 5 for a width of 6 and a read threshold of 4. Note that the write threshold is greater than the read threshold but less than the width. In this manner, a certain level of failure can be tolerated since more error code data slices with be written than are needed to recapture the data, but less than the desired level of fault tolerance. A rebuilder function insures that the difference between the write threshold and width will be automatically corrected (e.g., the rebuilder function will insure that DS unit 5 receives the new version of the data).

In this example, the storage module receives the write threshold number of acknowledgements (e.g., 5) prior to its timeout period expiring and the storage process proceeds to the example of FIG. 9. If, however, the storage module did not receive the write threshold number of acknowledgements prior to the timeout expiring, it may initiate a retry mechanism (e.g., resend the write commands) or may send the rollback command. If a DS storage unit receives a rollback command, it first determines whether it stored the new version and, if so, deletes it. In this example, each of DS storage units 1-4 and 6 would delete the new version if it received the rollback command. DS storage unit 5, however, would ignore the rollback command since it is not storing the new version of data.

In the example of FIG. 9, the storage module sends commit commands substantially in parallel (in time) to the DS storage units 1-4 and 6 and starts a second timeout period. As shown, the DS storage units receive their respective commit commands. In response to the commit command, DS storage units 1-4 and 6 make the new version of data visible by moving the pointer to the new version, but do delete the old version (e.g., the new version became visible and the old version became invisible). Since DS storage unit 5 does not include the new version of data, it did not receive a commit command and does not change its pointer. In addition, DS storage unit 5 may request the new version from the storage module.

In the example of FIG. 10, each of DS storage units 1-4 and 6 sends a commit acknowledgement to the storage module indicating that it has made the new version visible and still has the old version of data. In addition to sending the commit acknowledgement, each DS storage unit starts a finalize timeout period (e.g., a few millisecond to 10s of seconds). If a finalize command (which is discussed with reference to FIG. 11) is not received prior to the expiration of the commit timeout period, the DS storage unit deletes the new version of data and make the old version of data visible (e.g., adjust the pointer to point at the old version of data).

As the storage module receives the commit acknowledgements, it determines whether it has received a write threshold number of acknowledgements within the timeout period. In this example, the storage module received a write threshold number of commit acknowledgements. As such, this example write process moves to the finalize stage, which is discussed with reference to FIG. 11.

If the write threshold number of commit acknowledgements is not received during the second timeout period, the storage module may evoke a retry mechanism (e.g., resend the commit commands) or issue undo commands. If a DS storage unit receives an undo command, it first determines whether it stored the new version and, if so, deletes it and makes the old version of data visible. In this example, each of DS storage units 1-4 and 6 would delete the new version and make the old version visible if it received the undo command. DS storage unit 5, however, would ignore the undo command since it is not storing the new version of data.

In the example of FIG. 11, the storage module sends finalize commands substantially in parallel (in time) to the DS storage units 1-4 and 6. In response to receiving a finalize command, each of DS storage units 1-4 and 6 verifies the new version of data and deletes the old version. Since DS storage unit 5 does not include the new version of data, it does not delete the old version, which is still visible (e.g., the pointer is pointing to the old version). In addition, DS storage unit 5 may request the new version from the storage module.

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “coupled to” and/or “coupling” and/or includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “operable to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1.

The present invention has also been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claimed invention.

The present invention has been described above with the aid of functional building blocks illustrating the performance of certain significant functions. The boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality. To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claimed invention. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof. 

1. A method for execution by a dispersed storage (DS) processing module, the method comprises: issuing a plurality of write commands to a plurality of DS storage units; receiving a write acknowledgement from one of the plurality of DS storage units to produce a received write acknowledgement; issuing a plurality of commit commands to the plurality of DS storage units when a write threshold number of the received write acknowledgements have been received; receiving a commit acknowledgement from a DS storage unit of the plurality of DS storage units to produce a received commit acknowledgement; and issuing a plurality of finalize commands to the plurality of DS storage units when a write threshold number of the received commit acknowledgements have been received.
 2. The method of claim 1, wherein a write command of the plurality of write commands comprises: a write operation code that includes a write instruction and an address of a corresponding one of the plurality of DS storage units; and a data slice of a plurality of data slices.
 3. The method of claim 1, wherein the issuing the plurality of commit commands further comprises: issuing the plurality of commit commands when the write threshold number of the received write acknowledgements have been received within a given time period; and when the write threshold number of the received write acknowledgements have been not been received within the given time period, issuing a plurality of rollback commands to the plurality of DS storage units.
 4. The method of claim 1, where the issuing the plurality of finalize commands further comprises: issuing the plurality of finalize commands when the write threshold number of the received commit acknowledgements have been received within a given time period; and when the write threshold number of the received commit acknowledgements have been not been received within the given time period, issuing a plurality of undo commands to the plurality of DS storage units.
 5. The method of claim 1 further comprises: updating a DS virtual address table subsequent to issuing the plurality of finalize commands.
 6. A method for execution by a dispersed storage (DS) storage unit, the method comprises: receiving a write command regarding a data slice; transmitting a write acknowledgement in response to receiving the write command; receiving a commit command regarding the data slice within a commit time period; transmitting a commit acknowledgement in response to receiving the commit command; and receiving a finalize command regarding the data slice within a finalize time period.
 7. The method of claim 6 further comprises: in response to receiving the write command, storing a new version of the data slice in a non-visible manner; and maintaining an old version of the data slice in a visible manner.
 8. The method of claim 7 further comprises: in response to receiving the commit command, making the new version of the data slice visible; and making the older version of the data slice not visible.
 9. The method of claim 8 further comprises: in response to receiving the finalize command, deleting the old version of data slice.
 10. The method of claim 6 further comprises: when the commit command is not received within the commit time period, deleting a new version of the data slice.
 11. The method of claim 6 further comprises: prior to receiving the finalize command, receiving a rollback command; and in response to the rollback command, deleting a new version of the data slice.
 12. The method of claim 6 further comprises: after receiving the finalize command, receiving an undo command; and in response to the undo command, deleting a new version of the data slice; and making the older version of the data slice visible.
 13. The method of claim 8 further comprises: when the finalize command is not received within the finalize time period, deleting a new version of the data slice; and making the older version of the data slice visible.
 14. A dispersed storage (DS) processing module comprises: an interface module; and a processing module operable to: issue, via the interface module, a plurality of write commands to a plurality of DS storage units; receive, via the interface module, a write acknowledgement from one of the plurality of DS storage units to produce a received write acknowledgement; issue, via the interface module, a plurality of commit commands to the plurality of DS storage units when a write threshold number of the received write acknowledgements have been received; receive, via the interface module, a commit acknowledgement from a DS storage unit of the plurality of DS storage units to produce a received commit acknowledgement; and issue, via the interface module, a plurality of finalize commands to the plurality of DS storage units when a write threshold number of the received commit acknowledgements have been received.
 15. The DS processing module of claim 14, wherein a write command of the plurality of write commands comprises: a write operation code that includes a write instruction and an address of a corresponding one of the plurality of DS storage units; and a data slice of a plurality of data slices.
 16. The DS processing module of claim 14, wherein the processing module issuing the plurality of commit commands further comprises: issuing the plurality of commit commands when the write threshold number of the received write acknowledgements have been received within a given time period; and when the write threshold number of the received write acknowledgements have been not been received within the given time period, issuing a plurality of rollback commands to the plurality of DS storage units.
 17. The DS processing module of claim 14, wherein the processing module issuing the plurality of finalize commands further comprises: issuing the plurality of finalize commands when the write threshold number of the received commit acknowledgements have been received within a given time period; and when the write threshold number of the received commit acknowledgements have been not been received within the given time period, issuing a plurality of undo commands to the plurality of DS storage units.
 18. The DS processing module of claim 14, wherein the processing module is further operable to: update a DS virtual address table subsequent to issuing the plurality of finalize commands.
 19. A dispersed storage (DS) storage unit comprises: an interface module; memory; and a processing module operable to: receive, via the interface module, a write command regarding a data slice; transmit, via the interface module, a write acknowledgement in response to receiving the write command; receive, via the interface module, a commit command regarding the data slice within a commit time period; transmit, via the interface module, a commit acknowledgement in response to receiving the commit command; and receive, via the interface module, a finalize command regarding the data slice within a finalize time period.
 20. The DS storage unit of claim 19 wherein the processing module is further operable to: in response to receiving the write command, facilitate storing a new version of the data slice in the memory in a non-visible manner; and facilitate maintaining an old version of the data slice visible in the memory.
 21. The DS storage unit of claim 20 wherein the processing module is further operable to: in response to commit command, facilitate making the new version of the data slice visible in the memory; and facilitate making the old version of the data slice not visible in the memory.
 22. The DS storage unit of claim 21 wherein the processing module is further operable to: in response to receiving the finalize command, facilitate deleting the old version of data slice from the memory.
 23. The DS storage unit of claim 19 wherein the processing module is further operable to: when the commit command is not received within the commit time period, facilitate deleting a new version of the data slice from the memory.
 24. The DS storage unit of claim 19 wherein the processing module is further operable to: prior to receiving the finalize command, receive a rollback command; and in response to the rollback command, facilitate deleting a new version of the data slice from the memory.
 25. The DS storage unit of claim 20 wherein the processing module is further operable to: after receiving the finalize command, receive an undo command; and in response to the undo command, facilitate deleting a new version of the data slice from the memory; and facilitate making the older version of the data slice visible in the memory.
 26. The DS storage unit of claim 21 wherein the processing module is further operable to: when the finalize command is not received within the finalize time period, facilitate deleting a new version of the data slice from the memory; and facilitate making the older version of the data slice visible in the memory. 